Method and apparatus for annotating a call

ABSTRACT

Various aspects disclosed herein are directed to different types of personal assistant techniques for facilitating call event notation, tagging, calendaring, and etc., particularly those implemented on mobile communication devices. Users of mobile devices are provided with a relatively easy way to record and organize personal notes relating to one or more selected telephone conversations conducted by the user. Users can also manage notes, tasks, and schedule items related to the user&#39;s contacts and social network(s). In at least one embodiment, a Mobile Application running on a user&#39;s mobile device may be configured or designed to automatically detect an end of phone call event at the mobile device, and to automatically display a “pop-up” dialog GUI prompting the user to record a personalized note or other content (if desired), to be associated with the phone call which just ended.

RELATED APPLICATION DATA

This application is a continuation application of co-pending U.S. patentapplication Ser. No. 14/834,442, titled “METHOD AND APPARATUS FORPRODUCING A PROMPT ON A MOBILE DEVICE”, now U.S. Pat. No. 9,473,618,which is a continuation application of co-pending U.S. patentapplication Ser. No. 14/294,495, titled “AUTOMATED PROMPTING TECHNIQUESIMPLEMENTED VIA MOBILE DEVICES AND SYSTEMS”, now U.S. Pat. No.9,118,774, which is a continuation application of U.S. patentapplication Ser. No. 13/798,009, titled “AUTOMATED PROMPTING TECHNIQUESIMPLEMENTED VIA MOBILE DEVICES AND SYSTEMS”, now U.S. Pat. No.8,750,836, which is a continuation application of U.S. patentapplication Ser. No. 13/494,025, titled “AUTOMATED NOTATION TECHNIQUESIMPLEMENTED VIA MOBILE DEVICES AND/OR COMPUTER NETWORKS”, now U.S. Pat.No. 8,417,233, which claims the benefits of U.S. Provisional ApplicationSer. No. 61/496,460, titled “AUTOMATED NOTATION TECHNIQUES IMPLEMENTEDVIA MOBILE DEVICES AND/OR COMPUTER NETWORKS”, filed on Jun. 13, 2011.Each of these applications is incorporated herein by reference in itsentirety and for all purposes.

BACKGROUND

The present disclosure relates to automated techniques for communicationdevices. More particularly, the present disclosure relates to automatednotation techniques implemented via mobile devices and/or computernetworks.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a simplified block diagram of a specific exampleembodiment of an Automated Notation System (ANS) which may beimplemented in network portion 100;

FIG. 2 is a simplified block diagram of an exemplary Mobile Device 200in accordance with a specific embodiment;

FIG. 3 illustrates an example embodiment of a server system 380 whichmay be used for implementing various aspects/features described herein;

FIG. 4 shows a diagrammatic representation of machine in the exemplaryform of a client (or end user) computer system 400 within which a set ofinstructions, for causing the machine to perform any one or more of themethodologies discussed herein, may be executed;

FIG. 5 illustrates an example of a functional block diagram of anAutomated Notation Server System in accordance with a specificembodiment;

FIG. 6 shows an example screenshot of an email interface 600 inaccordance with a specific embodiment;

FIGS. 7-8 illustrate various example embodiments of different AutomatedNotation System procedures and/or procedural flows which may be used forfacilitating activities relating to one or more of the AutomatedNotation System aspects disclosed herein; and

FIGS. 9-22 illustrate example screenshots of various GUIs which may beused for facilitating activities relating to one or more of theAutomated Notation aspects disclosed herein.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS Overview

Various aspects described or referenced herein are directed to differentmethods, systems, and computer program products relating to automatedpersonal assistant techniques implemented via mobile devices and/orcomputer networks for facilitating call event notation, tagging,calendaring, and etc.

Various aspects described or referenced herein are directed to differentmethods, systems, and computer program products relating to automatedpersonal assistant techniques implemented via mobile devices and/orcomputer networks for facilitating call event notation, tagging,calendaring, and etc.

In at least one embodiment, various aspects are directed to differentmethod(s), system(s) and/or computer program product(s) for operating amobile communication device associated with a user, in which at leastone processor is caused to execute a plurality of instructions for:identifying a set of threshold criteria for causing automatic display,at the mobile communication device, of a user interface prompting theuser to initiate a procedure at the mobile communication device;determining if an occurrence of an end of call (EOC) event has beendetected at the mobile communication device, the end of call (EOC) eventrelating to a termination of a phone call conducted at the mobilecommunication device; determining if the set of threshold criteria hasbeen satisfied; automatically displaying the user interface at themobile communication device if it is determined that: (i) the occurrenceof the end of call (EOC) event has been detected, and (ii) the set ofthreshold criteria has been satisfied, wherein the displaying of theuser interface includes a prompt to the user to initiate a procedure atthe mobile communication device; initiating the procedure at the mobilecommunication device in response to receiving input from the userauthorizing initiation of the procedure; wherein the initiating of theprocedure includes: (i) generating, using an input from the user, aportion of digital content; (ii) accessing information which includesdetails relating to the phone call; (iii) creating an electronic datafile which associates the portion of digital content with at least aportion of the details relating to the phone call; and; (iv) saving theelectronic data file at a storage device such that the electronic datafile is accessible to the user for future reference.

Additional method(s), system(s) and/or computer program product(s) maybe further operable to cause at least one processor to executeadditional instructions for causing the user interface to not bedisplayed after detection of the occurrence of the end of call (EOC)event if it is determined that the set of threshold criteria has notbeen satisfied. In some embodiments, the set of threshold criteriaincludes criteria selected from a group consisting of: time relatedcriteria, day/date related criteria, contact information criteria, callduration criteria, call frequency criteria, and call type criteria.

In some embodiments, the set of threshold criteria includes criteriaidentifying a time threshold value relating to a minimum call durationof the phone call, and additional method(s), system(s) and/or computerprogram product(s) may be further operable to cause at least oneprocessor to execute additional instructions for: automaticallydisplaying a user interface at the mobile communication device if it isdetermined that: (i) the occurrence of the end of call (EOC) event hasbeen detected, and (ii) the duration of the call at the mobilecommunication device has met or exceeded a minimum call duration timethreshold value.

In some embodiments, the set of threshold criteria includes instructionsfor enabling a display of a user interface in connection with at leastone communication event at the mobile communication device associatedwith an identified contact, the identified contact having associatedtherewith a set of contact information, and additional method(s),system(s) and/or computer program product(s) may be further operable tocause at least one processor to execute additional instructions for:analyzing call details relating to the phone call to determine whetherthe phone call is associated with the identified contact; and;automatically displaying the user interface at the mobile communicationdevice if it is determined that: (i) the occurrence of the end of call(EOC) event has been detected, and (ii) the phone call is associatedwith the identified contact.

In some embodiments, the set of threshold criteria includes criteriaidentifying a date range for enabling the display of the user interface,and additional method(s), system(s) and/or computer program product(s)may be further operable to cause at least one processor to executeadditional instructions for: analyzing call details relating to thephone call to determine whether the phone call event occurred during thedate range; and; automatically displaying the user interface at themobile communication device if it is determined that: (i) the occurrenceof the end of call (EOC) event has been detected, and (ii) the phonecall event occurred during the date range.

In some embodiments, the set of threshold criteria includes criteriaidentifying a time range for enabling display of the user interface, andadditional method(s), system(s) and/or computer program product(s) maybe further operable to cause at least one processor to executeadditional instructions for: analyzing a set of call details relating tothe phone call to determine whether the phone call event occurred duringthe time range; and; automatically displaying the user interface at themobile communication device if it is determined that: (i) the occurrenceof the end of call (EOC) event has been detected, and (ii) the phonecall event occurred during the time range.

Additional method(s), system(s) and/or computer program product(s) maybe further operable to cause at least one processor to executeadditional instructions for: enabling the user of the mobilecommunication device to define display timeout criteria representing amaximum amount of time that the user interface is to be displayed at themobile communication device; waiting, after display of the userinterface message at the mobile communication device, to receive userresponse input from the user in response to the displayed user interfaceprompt; automatically removing display of the user interface at themobile communication device if no user response input is received afterthe user interface has been displayed for the maximum amount of time;and; initiating the procedure at the mobile communication device if auser response is received at the mobile communication device before themaximum amount of time has elapsed, wherein the user response representsan authorization from the user to initiate the procedure.

Additional method(s), system(s) and/or computer program product(s) maybe further operable to cause at least one processor to executeadditional instructions for: recording, using the mobile communicationdevice, a portion of audio content provided by the user, wherein theportion of digital content includes the portion of recorded audiocontent; transcribing the portion of audio content to thereby generate atext transcription content representing the portion of audio content;and; generating an electronic communication message which includes theportion of recorded audio content, the text transcription content, andat least a portion of the details relating to the detected phone callevent.

Additional objects, features and advantages of the various aspectsdescribed or referenced herein will become apparent from the followingdescription of its preferred embodiments, which description should betaken in conjunction with the accompanying drawings.

Specific Example Embodiments

Various techniques will now be described in detail with reference to afew example embodiments thereof as illustrated in the accompanyingdrawings. In the following description, numerous specific details areset forth in order to provide a thorough understanding of one or moreaspects and/or features described or reference herein. It will beapparent, however, to one skilled in the art, that one or more aspectsand/or features described or reference herein may be practiced withoutsome or all of these specific details. In other instances, well knownprocess steps and/or structures have not been described in detail inorder to not obscure some of the aspects and/or features described orreference herein.

One or more different inventions may be described in the presentapplication. Further, for one or more of the invention(s) describedherein, numerous embodiments may be described in this patentapplication, and are presented for illustrative purposes only. Thedescribed embodiments are not intended to be limiting in any sense. Oneor more of the invention(s) may be widely applicable to numerousembodiments, as is readily apparent from the disclosure. Theseembodiments are described in sufficient detail to enable those skilledin the art to practice one or more of the invention(s), and it is to beunderstood that other embodiments may be utilized and that structural,logical, software, electrical and other changes may be made withoutdeparting from the scope of the one or more of the invention(s).Accordingly, those skilled in the art will recognize that the one ormore of the invention(s) may be practiced with various modifications andalterations. Particular features of one or more of the invention(s) maybe described with reference to one or more particular embodiments orfigures that form a part of the present disclosure, and in which areshown, by way of illustration, specific embodiments of one or more ofthe invention(s). It should be understood, however, that such featuresare not limited to usage in the one or more particular embodiments orfigures with reference to which they are described. The presentdisclosure is neither a literal description of all embodiments of one ormore of the invention(s) nor a listing of features of one or more of theinvention(s) that must be present in all embodiments.

Headings of sections provided in this patent application and the titleof this patent application are for convenience only, and are not to betaken as limiting the disclosure in any way.

Devices that are in communication with each other need not be incontinuous communication with each other, unless expressly specifiedotherwise. In addition, devices that are in communication with eachother may communicate directly or indirectly through one or moreintermediaries.

A description of an embodiment with several components in communicationwith each other does not imply that all such components are required. Tothe contrary, a variety of optional components are described toillustrate the wide variety of possible embodiments of one or more ofthe invention(s).

Further, although process steps, method steps, algorithms or the likemay be described in a sequential order, such processes, methods andalgorithms may be configured to work in alternate orders. In otherwords, any sequence or order of steps that may be described in thispatent application does not, in and of itself, indicate a requirementthat the steps be performed in that order. The steps of describedprocesses may be performed in any order practical. Further, some stepsmay be performed simultaneously despite being described or implied asoccurring non-simultaneously (e.g., because one step is described afterthe other step). Moreover, the illustration of a process by itsdepiction in a drawing does not imply that the illustrated process isexclusive of other variations and modifications thereto, does not implythat the illustrated process or any of its steps are necessary to one ormore of the invention(s), and does not imply that the illustratedprocess is preferred.

When a single device or article is described, it will be readilyapparent that more than one device/article (whether or not theycooperate) may be used in place of a single device/article. Similarly,where more than one device or article is described (whether or not theycooperate), it will be readily apparent that a single device/article maybe used in place of the more than one device or article.

The functionality and/or the features of a device may be alternativelyembodied by one or more other devices that are not explicitly describedas having such functionality/features. Thus, other embodiments of one ormore of the invention(s) need not include the device itself.

Techniques and mechanisms described or reference herein will sometimesbe described in singular form for clarity. However, it should be notedthat particular embodiments include multiple iterations of a techniqueor multiple instantiations of a mechanism unless noted otherwise.

Various aspects disclosed herein are directed to different types ofautomated personal assistant techniques for facilitating call eventnotation, tagging, calendaring, and etc., particularly those implementedon mobile devices. For reference purposes, such automated techniques maybe referred to herein as “Automated Notation” techniques, oralternatively may be referred to herein as “Tote Note” techniques. In atleast one embodiment, a “Tote Note” may represent a personalized set ofcontent (e.g., text, audio, video, images.) relating to a user-basedevent (such as the end of a telephone call, for example). As describedin greater detail herein, the various automated Tote Note techniquesdescribed herein may be utilized to facilitate the generation of one ormore personalized Tote Notes.

In at least one embodiment, the Tote Note technique(s) provides a userof a mobile communication device with a relatively easy way to recordand organize personal notes relating to one or more selected telephoneconversations conducted by the user. It can also be used to managenotes, tasks, and to schedule items related to the user's contacts andsocial network(s). In at least one embodiment, a Tote Notes Application(TNA) running on a user's mobile device (such as, for example, aniPhone, Android-based smart phone, PDA, etc.) may be configured ordesigned to automatically detect an end of phone call event at themobile device, and to automatically display a “pop-up” dialog GUIprompting the user to record a Tote Note (if desired), to be associatedwith the phone call which just ended.

Example Block Diagram Description

FIG. 1 illustrates a simplified block diagram of a specific exampleembodiment of an Automated Notation System (ANS) which may beimplemented in network portion 100. As described in greater detailherein, different embodiments of personal automated note-taking systemmay be configured, designed, and/or operable to provide variousdifferent types of operations, functionalities, and/or featuresgenerally relating to Automated Notation System technology. Further, asdescribed in greater detail herein, many of the various operations,functionalities, and/or features of the Automated Notation System(s)disclosed herein may provide different types of advantages and/orbenefits to different entities interacting with the Automated NotationSystem(s).

According to different embodiments, at least some Automated NotationSystem(s) may be configured, designed, and/or operable to provide anumber of different advantages and/or benefits and/or may be operable toinitiate, and/or enable various different types of operations,functionalities, and/or features, such as, for example, one or more ofthe following (or combinations thereof):

-   -   The “Tote Notes” personal automated note-taking system is unique        and innovative software productivity tool which enables users to        record and store personal notes of their interactions with        selected individuals, with an emphasis upon mobile phone calls,        and allows those notes to be stored within the users email        system and/or other types of communications, notes, databases        and/or logs.    -   In at least one embodiment, at the conclusion of a mobile phone        call, or by manually starting the Tote Note Application, the        user is prompted to ‘record’ a Tote Note.    -   In at least one embodiment, the Tote Note Application records        the user's voice and transcribes his/her words in to text. These        data are packaged and attached to an email automatically        generated by the ANS.    -   The ANS populates the email subject heading with specific        information related to the call or personal interaction,        including: the marketing name of the product as an identifier,        the name of the person with whom the phone call or contact        occurred; and the date and time of the note, which is        approximately the same time as the date and time of the phone        call or personal interaction. In at least one embodiment, it may        also include the duration of the call.    -   The content of at least one email may include general notes,        follow up tasks, calendar items and appointments, and more.    -   The user has the option of configuring his or her own email        system to automatically sort and/or organize the emails by        contact name.    -   The ANS is available as a stand-alone product or as an API        module. The API module provides the same functionality as the        stand-alone product, but is designed to integrate with any        number of other software products, CRM systems, and proprietary        record-keeping and management systems.    -   The ANS may be configured to automatically initiate one or more        Tote Note activities in response to events/conditions which        match predetermined business rules, such as, for example, during        specified hours and days, such as “business hours” and etc.    -   The ANS may be configured to automatically initiate one or more        Tote Note activities in response to identifying activities        relating to one or more specified contacts.    -   Automatically populates subject field with specific information        from the name and date of the contact.    -   Software understands who you spoke to and when you spoke, so it        helps to easily organize and track selected phone calls.    -   Gives users the ability to make note of and track one or more        mobile phone call interactions.    -   Provides an email or text message which may be searched,        archived, and organized.    -   May be integrated with other systems, such as the users email        software/client, or any number of third party databases and        software tools.    -   Engages the user automatically at the conclusion of a mobile        phone call without having to manually start.    -   In one embodiment, software records voice and transcribes text        simultaneously.    -   In another embodiment, components of the ANS may relay audio        data to remote server for transcription and delivery.    -   Automatically places voice and text-based information in to an        electronic package/folder that is ready to be transmitted either        separately or together to a preselected destination, such as,        but not limited to, an email address, computer server, or a        phone number.    -   Imports contact information from phone module to be used within        electronic correspondence as a unique identifier.    -   In one embodiment, interprets voice data to perform commands,        which may include, but is not limited to, setting calendar        items, making phone calls, updating social media, etc.    -   Automatically places note information in to a correspondence        medium in multiple formats, such as email or text messages or        other electronic message formats.

According to different embodiments, the Automated Notation System 100may include a plurality of different types of components, devices,modules, processes, systems, etc., which, for example, may beimplemented and/or instantiated via the use of hardware and/orcombinations of hardware and software. For example, as illustrated inFIG. 1, the Automated Notation System may include one or more of thefollowing types of systems, components, devices, processes, etc. (orcombinations thereof):

-   -   Automated Notation Server System(s) 120—In at least one        embodiment, the Automated Notation Server System(s) may be        operable to perform and/or implement various types of functions,        operations, actions, and/or other features such as those        described or referenced herein (e.g., such as those illustrated        and/or described with respect to FIGS. 4 and 5).    -   Publisher/Content Provider System component(s) 140    -   Client Computer System (s) 130    -   3^(rd) Party System(s) 150    -   Internet & Cellular Network(s) 110    -   Remote Database System(s) 180    -   Remote Server System(s) 170    -   Mobile Device(s) 160—In at least one embodiment, the Mobile        Device(s) may be operable to perform and/or implement various        types of functions, operations, actions, and/or other features        such as those described or referenced herein (e.g., such as        those illustrated and/or described with respect to FIG. 2).    -   etc.

In at least one embodiment, the Automated Notation System may beoperable to utilize and/or generate various different types of dataand/or other types of information when performing specific tasks and/oroperations. This may include, for example, input data/information and/oroutput data/information. For example, in at least one embodiment, theAutomated Notation System may be operable to access, process, and/orotherwise utilize information from one or more different types ofsources, such as one or more local and/or remote memories, devicesand/or systems. Additionally, in at least one embodiment, the AutomatedNotation System may be operable to generate one or more different typesof output data/information, which, for example, may be stored in memoryof one or more local and/or remote devices and/or systems. Examples ofdifferent types of input data/information and/or output data/informationwhich may be accessed and/or utilized by the Automated Notation Systemmay include, but are not limited to, one or more of those describedand/or referenced herein.

According to specific embodiments, multiple instances or threads of theAutomated Notation System may be concurrently implemented and/orinitiated via the use of one or more processors and/or othercombinations of hardware and/or hardware and software. For example, inat least some embodiments, various aspects, features, and/orfunctionalities of the Automated Notation System may be performed,implemented and/or initiated by one or more of the various systems,components, systems, devices, procedures, processes, etc., describedand/or referenced herein.

In at least one embodiment, a given instance of the Automated NotationSystem may access and/or utilize information from one or more associateddatabases. In at least one embodiment, at least a portion of thedatabase information may be accessed via communication with one or morelocal and/or remote memory devices. Examples of different types of datawhich may be accessed by the Automated Notation System may include, butare not limited to, one or more of those described and/or referencedherein.

According to different embodiments, one or more different threads orinstances of the Automated Notation System may be initiated in responseto detection of one or more conditions or events satisfying one or moredifferent types of minimum threshold criteria for triggering initiationof at least one instance of the Automated Notation System. Variousexamples of conditions or events which may trigger initiation and/orimplementation of one or more different threads or instances of theAutomated Notation System may include, but are not limited to, one ormore of those described and/or referenced herein.

It may be appreciated that the Automated Notation System of FIG. 1 isbut one example from a wide range of Automated Notation Systemembodiments which may be implemented. Other embodiments of the AutomatedNotation System (not shown) may include additional, fewer and/ordifferent components/features that those illustrated in the exampleAutomated Notation System embodiment of FIG. 1.

Example Use Case Scenarios

The following examples are intended to help illustrate some of thevarious types of functions, operations, actions, and/or other featureswhich may be provided by the Automated Notation System. For purposes ofillustration, at least some of the examples are described herein by wayof reference to FIGS. 9-17 of the drawings.

FIGS. 9-17 illustrate respective example screenshots of various GUIswhich may be used for facilitating activities relating to one or more ofthe Automated Notation aspects disclosed herein. In at least oneembodiment, at least a portion of the GUIs may be configured or designedfor use at one or more mobile devices.

FIG. 9 shows an example sequence of GUIs (e.g., screenshots) which maybe displayed to a user in connection with one or more of the features,operations and/or techniques of the Automated Notation System and/orTote Note Application.

As illustrated in the example embodiment of FIG. 9, the AutomatedNotation GUI 900 may be operable to facilitate, initiate and/or performone or more of the following operation(s)/action(s) (or combinationsthereof):

-   -   GUI 902 illustrates an example of a typical “home screen” for a        mobile device, where the client application has been installed        and is running, and is displayed as an icon in one or more of        several locations.    -   GUI 904 shows an example screenshot GUI which may be displayed        at the user's mobile device to help facilitate Tote Note        Application setup and configuration options. Configuration        options are modified by the user, and based upon user        preferences, which, for example, may include, but are not        limited to: hours of operation, output options, pre-selection of        user lists for triggering, timing/duration features of the        client application, destination of output data, calendar        settings, and more.    -   GUI 906 shows an example screenshot GUI which may be displayed        at the user's mobile device to help facilitate user engagement        mode activities, such as, for example, where triggering options        have been satisfied and the Tote Note Application is activated        at the user's mobile device and is seeking the user's        commands/instructions.    -   GUI 908 shows an example screenshot GUI which may be displayed        at the user's mobile device to help facilitate Tote Note        recording mode activities, such as, for example, where        triggering events and user commands have activated client        application to (in one embodiment) record and/or transcribe        and/or interpret user's spoken word(s).    -   GUI 910 shows an example screenshot GUI which may be displayed        at the user's mobile device to help facilitate “send” mode        activities, such as, for example, where input data is being        compiled and output data is being generated as (in one        embodiment) a text message or email message or other form of        electronic correspondence.    -   GUI 912 shows an example screenshot GUI which may be displayed        at the user's mobile device to help facilitate manual activation        mode activities, such as, for example, where the user manually        activates software by (in one embodiment) selecting from the        contact database or phone log/history.

Example User Scenario for Mobile Device

For purposes of illustration, a example scenario is described below inwhich a user operates the Tote Note Application at the users mobiledevice based upon facts/assumptions provided in the example.

-   -   User installs application upon mobile device.    -   User configures the Tote Note Application settings and options        (see, e.g., example GUIs of FIGS. 13-19)    -   User places a call at 2:25PM on Thursday, and stays on the call        for approximately 5 minutes.    -   At the conclusion of the call, user is automatically prompted by        the Tote Note Application, inquiring, “Would you like to record        a Tote Note for this call?” (e.g., FIG. 10)    -   User selects “Yes”.    -   A Tote Note Recording GUI is displayed (e.g., FIG. 11) which        includes a timer, indicating that the mobile device is recording        personal notes related to the preceding phone call.    -   User taps the “send” button. (e.g., FIG. 11)    -   Tote Note Application acquires metadata and other information        relating to the identified call event, and transmits (e.g.,        FIG. 12) at least a portion of the Tote Note data to the        Automated Notation Server System and/or other remote system(s).        In at least one embodiment, the recorded audio portion of the        Tote Note may be automatically sent to a transcription server        for transcription of the audio content into text.    -   Mobile device is returned to its normal state.    -   Use receives an email in pre-determined email inbox, which        contains audio recording of the personal note and transcribed        text of the personal note. (e.g., FIG. 6)

Example User Scenario for Mobile Device with Server System

For purposes of illustration, a second example scenario is describedbelow in which a user operates the Tote Note Application at the usersmobile device based upon facts/assumptions provided in the example.

-   -   User installs Tote Note Application at mobile device.    -   User configures the Tote Note Application settings to        automatically prompt for activation at the conclusion of phone        calls from a pre-selected contact named “David Flynn”. (e.g.,        via example GUI of FIG. 21)    -   David Flynn calls user at 2:25PM on Thursday, and stays on the        call for approximately 7 minutes.    -   At the conclusion of the call, user is prompted by application,        inquiring, “Would you like to record a Tote Note for this call?”        (e.g., FIG. 10)    -   User selects “Add Calendar Event” (1006).    -   User speaks verbal commands in to device regarding an upcoming        calendar item. For example, “Set Appointment for lunch with        David Flynn next Tuesday 12:30 PM at the sandwich shop.” (e.g.,        FIG. 11)    -   Audio data is recorded by device and automatically        transmitted/streamed to the Automated Notation Server System        and/or other remote server system.    -   Automated Notation Server System automatically interprets the        audio recording and associated metadata, generates Tote Note,        and automatically creates a calendar appointment in the user's        calendar per instructed time, using contact name and other data        received from the call record. In at least one embodiment, the        Automated Notation Server System may also be configured or        designed to automatically and/or dynamically identify one or        more contacts relating to a Tote Note created calendar event,        and may automatically send calendar invites and/or other        communications to the identified contacts.

In at least one embodiment, the Automated Notation Server System mayautomatically and periodically “POLL” mobile device to dynamicallydetermine whether there are any current or outstanding Tote Note relatedactivities to be performed. To see if there are any embedded, and/orafter voicemail sends a text to the other person, or calendaring, andinvites.

FIG. 2 is a simplified block diagram of an exemplary Mobile Device 200in accordance with a specific embodiment. In at least one embodiment,the Mobile Device may include Tote Note Application component(s) whichhave been configured or designed to provide functionality for enablingor implementing at least a portion of the various Automated NotationSystem techniques at the Mobile Device. In at least one embodiment, theMobile Device 200 may be operable to perform and/or implement varioustypes of functions, operations, actions, and/or other features such as,for example, one or more of those described and/or referenced herein.

According to specific embodiments, various aspects, features, and/orfunctionalities of the Mobile Device may be performed, implementedand/or initiated by one or more of the following types of systems,components, systems, devices, procedures, processes, etc. (orcombinations thereof):

-   -   Processor(s) 210    -   Device Drivers 242    -   Memory 216    -   Interface(s) 206    -   Power Source(s)/Distribution 243    -   Geolocation module 246    -   Display(s) 235    -   I/O Devices 230    -   Audio/Video devices(s) 239    -   Peripheral Devices 231    -   Motion Detection module 240    -   User Identification/Authentication module 247    -   Client App Component(s) 260    -   Other Component(s) 268    -   UI Component(s) 262    -   Database Component(s) 264    -   Processing Component(s) 266    -   Software/Hardware Authentication/Validation 244    -   Wireless communication module(s) 245    -   Information Filtering module(s) 249    -   Operating mode selection component 248    -   Speech Processing module 254    -   Scanner/Camera 252    -   OCR Processing Engine 256    -   etc.

As illustrated in the example of FIG. 2 Mobile Device 200 may beimplemented as a mobile or handheld computing device which includes avariety of components, modules and/or systems for providing variousfunctionality. For example, as illustrated in FIG. 2, Mobile Device 200may include Tote Note Application components (e.g., 260), which, forexample, may include, but are not limited to, one or more of thefollowing (or combinations thereof):

-   -   UI Components 262 such as those illustrated, described, and/or        referenced herein.    -   Database Components 264 such as those illustrated, described,        and/or referenced herein.    -   Processing Components 266 such as those illustrated, described,        and/or referenced herein.    -   Other Components 268 which, for example, may include components        for facilitating and/or enabling the Mobile Device to perform        and/or initiate various types of operations, activities,        functions such as those described herein.

In at least one embodiment, the Tote Note Application component(s) maybe operable to perform and/or implement various types of functions,operations, actions, and/or other features such as, for example, one ormore of the following (or combinations thereof):

-   -   The Tote Note Application may be installed and operated at a        user's mobile communication device such as a mobile        telephone/smart phone device.    -   The Tote Note Application presents configuration options, which        may include, but are not limited to, hours of operation,        pre-selected contact names for the use with the system, options        related to time constraints associated with the application's        functions and/or features, rules for selecting individual        contact records, amongst other options.    -   The Tote Note Application may operate continually in the        background during user-specified times of operation.    -   Tote Note Application automatically activates at the conclusion        or end of a phone call and/or other triggering event(s).    -   In one embodiment, Tote Note Application provides interface to        collect audio recording of voice notes and transcription of        notes to text.    -   In one embodiment, the Tote Note Application records audio and        sends audio data, contact data, call data, call duration,        time/date data, and other data to a remote server for        transcription.    -   In one embodiment, the Tote Note Application transcribes audio        dictation to text locally at the mobile device.    -   The Tote Note Application may assemble input data, including but        not limited to voice audio data, transcribed text data in to        multiple formats, locational data, GPS data, time and date data,        calendar information, call data such as call duration, video and        graphic information    -   The Tote Note Application may automatically and/or dynamically        generate an outgoing message which may include several types of        date, metadata, and/or other information such as, for example,        one or more of the following (or combinations thereof):

o contact information (e.g., relating to person(s) which the user mayhave spoken to);

-   -   -   the date and time of the correspondence or call;        -   the duration of the call;        -   locational/GPS data;        -   voice/audio/transcribed input data (e.g., provided by the            user);        -   etc.

    -   In one embodiment information may be conveyed in a variety of        different electronic mediums and networks, which may include the        internet, wireless networks, and private/proprietary electronic        networks

    -   The Tote Note Application may automatically and/or dynamically        generate Tote Notes in email format, text message format,        calendar event format, and/or other types of formats.

    -   In one embodiment, the Tote Note Application interprets the        spoken and/or transcribed works, instructing and initiating        other electronic processes, which may include but is not limited        to making a phone call, sending an email, setting a calendar        appointment, etc.

    -   The Tote Note Application may be configured or designed to        facilitate access to various types of communication networks        such as, for example, one or more of the following (or        combinations thereof): the internet, wireless networks, a        private electronic networks, or proprietary electronic        communication systems, cellular networks, local area networks,        etc.

    -   In one embodiment, the Tote Note Application may automatically        access various types of information at the user's mobile        communication device such as, for example, one or more of the        following (or combinations thereof): contacts, call log history        data, GPS data, user profile data, etc.

    -   In at least one embodiment, the Tote Note Application may be        operable to access, send, receive, store, retrieve, and/or        acquire various types of data which may be used at the user's        mobile device and/or by other components/systems of the        Automated Notation System.

    -   In at least one embodiment, the Tote Note Application may        automatically and/or dynamically acquire and/or present        contextually relevant advertising information at the user's        mobile device.

    -   In at least one embodiment, the Tote Note Application may        communicate with the Automated Notation Server System to        automatically perform, initiate, manage, track, store, analyze,        and/or retrieve various types of data and/or other information        (such as, for example, call log data, contact data, email        messages, text messages, and other electronic correspondence)        which may be generated by (and/or used by) the Tote Note        Application and/or Automated Notation System.

According to specific embodiments, multiple instances or threads of theTote Note Application component(s) may be concurrently implementedand/or initiated via the use of one or more processors and/or othercombinations of hardware and/or hardware and software. For example, inat least some embodiments, various aspects, features, and/orfunctionalities of the Tote Note Application component(s) may beperformed, implemented and/or initiated by one or more of the followingtypes of systems, components, systems, devices, procedures, processes,etc., described and/or referenced herein.

According to different embodiments, one or more different threads orinstances of the Tote Note Application component(s) may be initiated inresponse to detection of one or more conditions or events satisfying oneor more different types of minimum threshold criteria for triggeringinitiation of at least one instance of the Tote Note Applicationcomponent(s). Various examples of conditions or events which may triggerinitiation and/or implementation of one or more different threads orinstances of the Tote Note Application component(s) may include, but arenot limited to, one or more of the following (or combinations thereof):

-   -   In one embodiment, one or more functions of the Tote Note        Application may be automatically triggered by the termination of        a phone call, whether intentionally ended by the user, or        intentionally ended by the other party on the telephone call, or        inadvertently through a poor signal (e.g. “dropped call) etc.,        and that phone call is of a duration that is at least XX        seconds. (e.g., where XX may be a value defined either within        software or by user-defined setting, such as, for example, XX=5        seconds, XX selected from a range of 1-300 seconds, etc.)    -   In one embodiment, one or more functions of the Tote Note        Application may be automatically activated or initiated at        conclusion of such phone calls during specified hours of the day        and week, as configured through the options and set up of the        application.    -   In another embodiment, one or more functions of the Tote Note        Application may be automatically activated or initiated at        conclusion of phone calls with specific contacts pre-selected        from the mobile device's contact database. In at least one        embodiment, the selection of the desired contacts may be        configured through the options and set up menus of the Tote Note        Application.    -   In another embodiment, one or more functions of the Tote Note        Application may be automatically activated or initiated manually        through a user interface, which may allow users to select from a        list of contacts stored on the mobile device.    -   In another embodiment, one or more functions of the Tote Note        Application may be automatically activated or initiated manually        through a user interface, which may allow users to select from a        list of contacts stored on the internet, or from a list of        contacts upon a remote server accessed through the internet, or        wireless network, or another private electronic network.    -   In another embodiment, one or more functions of the Tote Note        Application may be automatically activated or initiated upon        receipt of a voicemail or electronic message or communication        from another party.    -   In another embodiment, one or more functions of the Tote Note        Application may be automatically activated or initiated at        specified triggering events and/or conditions, as determined by        the user.    -   In another embodiment, one or more functions of the Tote Note        Application may be automatically activated or initiated at the        conclusion of specified calendar events.    -   In another embodiment, one or more functions of the Tote Note        Application may be automatically activated or initiated by        spoken voice command.    -   In at least one embodiment, a given instance of the Tote Note        Application component(s) may access and/or utilize information        from one or more associated databases. In at least one        embodiment, at least a portion of the database information may        be accessed via communication with one or more local and/or        remote memory devices. Examples of different types of data which        may be accessed by the Tote Note Application component(s) may        include, but are not limited to, one or more of those described        and/or referenced herein.    -   Input data may be automatically obtained by the Tote Note        Application, including but not limited to voice audio data,        transcribed text data, GPS/locational data, time and date data,        calendar information, video and graphic information, call log        data.    -   Input data related to contacts may be automatically obtained by        the Tote Note Application, which may include details including        but not limited to name, organization, telephone number, email        address, www address, mailing address, physical address, and        contact history.    -   Input data may be automatically obtained by the Tote Note        Application from a remote server or database, including but not        limited to voice audio data, transcribed text data,        GPS/locational data, time and date data, calendar information,        video and graphic information    -   Input data related to contacts may be automatically obtained by        the Tote Note Application from a remote server or database,        which may include details including but not limited to name,        organization, telephone number, email address, www address,        mailing address, physical address, and contact history.    -   Input data may also include content from third party publishers,        such as, for example, advertising information, alerts,        communications, contact data, phone log data, billing        information, etc.

According to different embodiments, Mobile Device 200 may furtherinclude, but is not limited to, one or more of the following types ofcomponents, modules and/or systems (or combinations thereof):

-   -   At least one processor 210. In at least one embodiment, the        processor(s) 210 may include one or more commonly known CPUs        which are deployed in many of today's consumer electronic        devices, such as, for example, CPUs or processors from the        Motorola or Intel family of microprocessors, etc. In an        alternative embodiment, at least one processor may be specially        designed hardware for controlling the operations of the Mobile        Device. In a specific embodiment, a memory (such as non-volatile        RAM and/or ROM) also forms part of CPU. When acting under the        control of appropriate software or firmware, the CPU may be        responsible for implementing specific functions associated with        the functions of a desired network device. The CPU preferably        accomplishes one or more these functions under the control of        software including an operating system, and any appropriate        applications software.    -   Memory 216, which, for example, may include volatile memory        (e.g., RAM), non-volatile memory (e.g., disk memory, FLASH        memory, EPROMs, etc.), unalterable memory, and/or other types of        memory. In at least one implementation, the memory 216 may        include functionality similar to at least a portion of        functionality implemented by one or more commonly known memory        devices such as those described herein and/or generally known to        one having ordinary skill in the art. According to different        embodiments, one or more memories or memory modules (e.g.,        memory blocks) may be configured or designed to store data,        program instructions for the functional operations of the Mobile        Device and/or other information relating to the functionality of        the various Automated Notation techniques described herein. The        program instructions may control the operation of an operating        system and/or one or more applications, for example. The memory        or memories may also be configured to store data structures,        metadata, timecode synchronization information, audio/visual        media content, asset file information, keyword taxonomy        information, advertisement information, and/or information/data        relating to other features/functions described herein. Because        such information and program instructions may be employed to        implement at least a portion of the Automated Notation        techniques described herein, various aspects described herein        may be implemented using machine readable media that include        program instructions, state information, etc. Examples of        machine-readable media include, but are not limited to, magnetic        media such as hard disks, floppy disks, and magnetic tape;        optical media such as CD-ROM disks; magneto-optical media such        as floptical disks; and hardware devices that are specially        configured to store and perform program instructions, such as        read-only memory devices (ROM) and random access memory (RAM).        Examples of program instructions include both machine code, such        as produced by a compiler, and files containing higher level        code that may be executed by the computer using an interpreter.    -   Interface(s) 206 which, for example, may include wired        interfaces and/or wireless interfaces. In at least one        implementation, the interface(s) 206 may include functionality        similar to at least a portion of functionality implemented by        one or more computer system interfaces such as those described        herein and/or generally known to one having ordinary skill in        the art. For example, in at least one implementation, the        wireless communication interface(s) may be configured or        designed to communicate with selected electronic game tables,        computer systems, remote servers, other wireless devices (e.g.,        PDAs, cell phones, player tracking transponders, etc.), etc.        Such wireless communication may be implemented using one or more        wireless interfaces/protocols such as, for example, 802.11        (WiFi), 802.15 (including Bluetooth™), 802.16 (WiMax), 802.22,        Cellular standards such as CDMA, CDMA2000, WCDMA, Radio        Frequency (e.g., RFID), Infrared, Near Field Magnetics, etc.    -   Device driver(s) 242. In at least one implementation, the device        driver(s) 242 may include functionality similar to at least a        portion of functionality implemented by one or more computer        system driver devices such as those described herein and/or        generally known to one having ordinary skill in the art.    -   At least one power source (and/or power distribution source)        243. In at least one implementation, the power source may        include at least one mobile power source (e.g., battery) for        allowing the Mobile Device to operate in a wireless and/or        mobile environment. For example, in one implementation, the        power source 243 may be implemented using a rechargeable,        thin-film type battery. Further, in embodiments where it is        desirable for the device to be flexible, the power source 243        may be designed to be flexible.    -   Geolocation module 246 which, for example, may be configured or        designed to acquire geolocation information from remote sources        and use the acquired geolocation information to determine        information relating to a relative and/or absolute position of        the Mobile Device.    -   Motion detection component 240 for detecting motion or movement        of the Mobile Device and/or for detecting motion, movement,        gestures and/or other input data from user. In at least one        embodiment, the motion detection component 240 may include one        or more motion detection sensors such as, for example, MEMS        (Micro Electro Mechanical System) accelerometers, that may        detect the acceleration and/or other movements of the Mobile        Device as it is moved by a user.    -   User Identification/Authentication module 247. In one        implementation, the User Identification module may be adapted to        determine and/or authenticate the identity of the current user        or owner of the Mobile Device. For example, in one embodiment,        the current user may be required to perform a log in process at        the Mobile Device in order to access one or more features.        Alternatively, the Mobile Device may be adapted to automatically        determine the identity of the current user based upon one or        more external signals such as, for example, an RFID tag or badge        worn by the current user which provides a wireless signal to the        Mobile Device for determining the identity of the current user.        In at least one implementation, various security features may be        incorporated into the Mobile Device to prevent unauthorized        users from accessing confidential or sensitive information.    -   One or more display(s) 235. According to various embodiments,        such display(s) may be implemented using, for example, LCD        display technology, OLED display technology, and/or other types        of conventional display technology. In at least one        implementation, display(s) 235 may be adapted to be flexible or        bendable. Additionally, in at least one embodiment the        information displayed on display(s) 235 may utilize e-ink        technology (such as that available from E Ink Corporation,        Cambridge, Mass., www.eink.com), or other suitable technology        for reducing the power consumption of information displayed on        the display(s) 235.    -   One or more user I/O Device(s) 230 such as, for example, keys,        buttons, scroll wheels, cursors, touchscreen sensors, audio        command interfaces, magnetic strip reader, optical scanner, etc.    -   Audio/Video device(s) 239 such as, for example, components for        displaying audio/visual media which, for example, may include        cameras, speakers, microphones, media presentation components,        wireless transmitter/receiver devices for enabling wireless        audio and/or visual communication between the Mobile Device 200        and remote devices (e.g., radios, telephones, computer systems,        etc.). For example, in one implementation, the audio system may        include componentry for enabling the Mobile Device to function        as a cell phone or two-way radio device.    -   Other types of peripheral devices 231 which may be useful to the        users of various Mobile Devices, such as, for example: PDA        functionality; memory card reader(s); fingerprint reader(s);        image projection device(s); social networking peripheral        component(s); etc.    -   Information filtering module(s) 249 which, for example, may be        adapted to automatically and dynamically generate, using one or        more filter parameters, filtered information to be displayed on        one or more displays of the mobile device. In one        implementation, such filter parameters may be customizable by        the player or user of the device. In some embodiments,        information filtering module(s) 249 may also be adapted to        display, in real-time, filtered information to the user based        upon a variety of criteria such as, for example, geolocation        information, casino data information, player tracking        information, etc.    -   Wireless communication module(s) 245. In one implementation, the        wireless communication module 245 may be configured or designed        to communicate with external devices using one or more wireless        interfaces/protocols such as, for example, 802.11 (WiFi), 802.15        (including Bluetooth™), 802.16 (WiMax), 802.22, Cellular        standards such as CDMA, CDMA2000, WCDMA, Radio Frequency (e.g.,        RFID), Infrared, Near Field Magnetics, etc.    -   Software/Hardware Authentication/validation components 244        which, for example, may be used for authenticating and/or        validating local hardware and/or software components,        hardware/software components residing at a remote device, game        play information, wager information, user information and/or        identity, etc.    -   Operating mode selection component 248 which, for example, may        be operable to automatically select an appropriate mode of        operation based on various parameters and/or upon detection of        specific events or conditions such as, for example: the mobile        device's current location; identity of current user; user input;        system override (e.g., emergency condition detected); proximity        to other devices belonging to same group or association;        proximity to specific objects, regions, zones, etc.        Additionally, the mobile device may be operable to automatically        update or switch its current operating mode to the selected mode        of operation. The mobile device may also be adapted to        automatically modify accessibility of user-accessible features        and/or information in response to the updating of its current        mode of operation.    -   Scanner/Camera Component(s) (e.g., 252) which may be configured        or designed for use in capturing images, recording video,        scanning documents, barcodes, etc.    -   OCR Processing Engine (e.g., 256) which, for example, may be        operable to perform image processing and optical character        recognition of images such as those captured by a mobile device        camera, for example.    -   Transcription Processing Component(s) (e.g., 241) which, for        example, may be operable to automatically and/or dynamically        initiate, perform, and/or facilitate transcription of audio        content into corresponding text-based content. In at least one        embodiment, the Transcription Processing Component(s) may        utilize the services of one or more remote transcription servers        for performing at least a portion of the transcription        processing. In at least one embodiment, the Automated Notation        Server System may initiate transcription of the Tote Note audio        content via use of an API to the Google Voice transcription        service (provided by Google, Inc.). In some embodiments, at        least a portion of the transcription may be performed at the        user's mobile communication device.    -   Speech Processing module (e.g., 254) which, for example, may be        operable to perform speech recognition, and may be operable to        perform speech-to-text conversion.    -   Etc.

FIG. 3 illustrates an example embodiment of a server system 380 whichmay be used for implementing various aspects/features described herein.In at least one embodiment, the server system 380 includes at least onenetwork device 360, and at least one storage device 370 (such as, forexample, a direct attached storage device). In one embodiment, serversystem 380 may be suitable for implementing at least some of theAutomated Notation techniques described herein.

In according to one embodiment, network device 360 may include a mastercentral processing unit (CPU) 362, interfaces 368, and a bus 367 (e.g.,a PCI bus). When acting under the control of appropriate software orfirmware, the CPU 362 may be responsible for implementing specificfunctions associated with the functions of a desired network device. Forexample, when configured as a server, the CPU 362 may be responsible foranalyzing packets; encapsulating packets; forwarding packets toappropriate network devices; instantiating various types of virtualmachines, virtual interfaces, virtual storage volumes, virtualappliances; etc. The CPU 362 preferably accomplishes at least a portionof these functions under the control of software including an operatingsystem (e.g. Linux), and any appropriate system software (such as, forexample, AppLogic™ software).

CPU 362 may include one or more processors 363 such as, for example, oneor more processors from the AMD, Motorola, Intel and/or MIPS families ofmicroprocessors. In an alternative embodiment, processor 363 may bespecially designed hardware for controlling the operations of serversystem 380. In a specific embodiment, a memory 361 (such as non-volatileRAM and/or ROM) also forms part of CPU 362. However, there may be manydifferent ways in which memory could be coupled to the system. Memoryblock 361 may be used for a variety of purposes such as, for example,caching and/or storing data, programming instructions, etc.

The interfaces 68 may be typically provided as interface cards(sometimes referred to as “line cards”). Alternatively, one or more ofthe interfaces 68 may be provided as on-board interface controllersbuilt into the system motherboard. Generally, they control the sendingand receiving of data packets over the network and sometimes supportother peripherals used with the server system 80. Among the interfacesthat may be provided may be FC interfaces, Ethernet interfaces, framerelay interfaces, cable interfaces, DSL interfaces, token ringinterfaces, Infiniband interfaces, and the like. In addition, variousvery high-speed interfaces may be provided, such as fast Ethernetinterfaces, Gigabit Ethernet interfaces, ATM interfaces, HSSIinterfaces, POS interfaces, FDDI interfaces, ASI interfaces, DHEIinterfaces and the like. Other interfaces may include one or morewireless interfaces such as, for example, 802.11 (WiFi) interfaces,802.15 interfaces (including Bluetooth™) 802.16 (WiMax) interfaces,802.22 interfaces, Cellular standards such as CDMA interfaces, CDMA2000interfaces, WCDMA interfaces, TDMA interfaces, Cellular 3G interfaces,etc.

Generally, one or more interfaces may include ports appropriate forcommunication with the appropriate media. In some cases, they may alsoinclude an independent processor and, in some instances, volatile RAM.The independent processors may control such communications intensivetasks as packet switching, media control and management. By providingseparate processors for the communications intensive tasks, theseinterfaces allow the master microprocessor 362 to efficiently performrouting computations, network diagnostics, security functions, etc.

In at least one embodiment, some interfaces may be configured ordesigned to allow the server system 380 to communicate with othernetwork devices associated with various local area network (LANs) and/orwide area networks (WANs). Other interfaces may be configured ordesigned to allow network device 360 to communicate with one or moredirect attached storage device(s) 370.

Although the system shown in FIG. 3 illustrates one specific networkdevice described herein, it is by no means the only network devicearchitecture on which one or more embodiments may be implemented. Forexample, an architecture having a single processor that handlescommunications as well as routing computations, etc. may be used.Further, other types of interfaces and media could also be used with thenetwork device.

Regardless of network device's configuration, it may employ one or morememories or memory modules (such as, for example, memory block 365,which, for example, may include random access memory (RAM)) configuredto store data, program instructions for the general-purpose networkoperations and/or other information relating to the functionality of thevarious Automated Notation techniques described herein. The programinstructions may control the operation of an operating system and/or oneor more applications, for example. The memory or memories may also beconfigured to store data structures, and/or other specific non-programinformation described herein.

Because such information and program instructions may be employed toimplement the systems/methods described herein, one or more embodimentsrelates to machine readable media that include program instructions,state information, etc. for performing various operations describedherein. Examples of machine-readable storage media include, but are notlimited to, magnetic media such as hard disks, floppy disks, andmagnetic tape; optical media such as CD-ROM disks; magneto-optical mediasuch as floptical disks; and hardware devices that may be speciallyconfigured to store and perform program instructions, such as read-onlymemory devices (ROM) and random access memory (RAM). Some embodimentsmay also be embodied in transmission media such as, for example, acarrier wave travelling over an appropriate medium such as airwaves,optical lines, electric lines, etc. Examples of program instructionsinclude both machine code, such as produced by a compiler, and filescontaining higher level code that may be executed by the computer usingan interpreter.

FIG. 4 shows a diagrammatic representation of machine in the exemplaryform of a client (or end user) computer system 400 within which a set ofinstructions, for causing the machine to perform any one or more of themethodologies discussed herein, may be executed. In alternativeembodiments, the machine operates as a standalone device or may beconnected (e.g., networked) to other machines. In a networkeddeployment, the machine may operate in the capacity of a server or aclient machine in server-client network environment, or as a peermachine in a peer-to-peer (or distributed) network environment. Themachine may be a personal computer (PC), a tablet PC, a set-top box(STB), a Personal Digital Assistant (PDA), a cellular telephone, a webappliance, a network router, switch or bridge, or any machine capable ofexecuting a set of instructions (sequential or otherwise) that specifyactions to be taken by that machine. Further, while only a singlemachine is illustrated, the term “machine” may also be taken to includeany collection of machines that individually or jointly execute a set(or multiple sets) of instructions to perform any one or more of themethodologies discussed herein.

The exemplary computer system 400 includes a processor 402 (e.g., acentral processing unit (CPU), a graphics processing unit (GPU) orboth), a main memory 404 and a static memory 406, which communicate withat least one other via a bus 408. The computer system 400 may furtherinclude a video display unit 410 (e.g., a liquid crystal display (LCD)or a cathode ray tube (CRT)). The computer system 400 also includes analphanumeric input device 412 (e.g., a keyboard), a user interface (UI)navigation device 414 (e.g., a mouse), a disk drive unit 416, a signalgeneration device 418 (e.g., a speaker) and a network interface device420.

The disk drive unit 416 includes a machine-readable medium 422 on whichis stored one or more sets of instructions and data structures (e.g.,software 424) embodying or utilized by any one or more of themethodologies or functions described herein. The Tote Note Application424 may also reside, completely or at least partially, within the mainmemory 404 and/or within the processor 402 during execution thereof bythe computer system 400, the main memory 404 and the processor 402 alsoconstituting machine-readable media.

The Tote Note Application 424 may further be transmitted or receivedover a network 426 via the network interface device 420 utilizing anyone of a number of well-known transfer protocols (e.g., HTTP).

While the machine-readable medium 422 is shown in an exemplaryembodiment to be a single medium, the term “machine-readable medium” maybe taken to include a single medium or multiple media (e.g., acentralized or distributed database, and/or associated caches andservers) that store the one or more sets of instructions. The term“machine-readable medium” may also be taken to include any medium thatis capable of storing, encoding or carrying a set of instructions forexecution by the machine and that cause the machine to perform any oneor more of the methodologies of the present invention, or that iscapable of storing, encoding or carrying data structures utilized by orassociated with such a set of instructions. The term “machine-readablemedium” may accordingly be taken to include, but not be limited to,solid-state memories, optical and magnetic media, and carrier wavesignals. Although an embodiment of the present invention has beendescribed with reference to specific exemplary embodiments, it may beevident that various modifications and changes may be made to theseembodiments without departing from the broader spirit and scope of theinvention. Accordingly, the specification and drawings are to beregarded in an illustrative rather than a restrictive sense.

According to various embodiments, Client Computer System 400 may includea variety of components, modules and/or systems for providing varioustypes of functionality. For example, in at least one embodiment, ClientComputer System 400 may include a web browser application which isoperable to process, execute, and/or support the use of scripts (e.g.,JavaScript, AJAX, etc.), Plug-ins, executable code, virtual machines,vector-based web animation (e.g., Adobe Flash), etc.

In at least one embodiment, the web browser application may beconfigured or designed to instantiate components and/or objects at theClient Computer System in response to processing scripts, instructions,and/or other information received from a remote server such as a webserver. Examples of such components and/or objects may include, but arenot limited to, one or more of the following (or combinations thereof):

-   -   User Interface (UI) Components such as those illustrated,        described, and/or referenced herein.    -   Database Components such as those illustrated, described, and/or        referenced herein.    -   Processing Components such as those illustrated, described,        and/or referenced herein.    -   Other Components which, for example, may include components for        facilitating and/or enabling the Client Computer System to        perform and/or initiate various types of operations, activities,        functions such as those described herein.

FIG. 5 illustrates an example of a functional block diagram of anAutomated Notation Server System in accordance with a specificembodiment. In at least one embodiment, the Automated Notation ServerSystem may be operable to perform and/or implement various types offunctions, operations, actions, and/or other features such as, forexample, one or more of the following (or combinations thereof):

-   -   In one embodiment, the Server System functions may establish        user profiles to store and maintain user accounts, user data,        and user settings, and output data.    -   In another embodiment server system data may be obtained by the        mobile device or mobile device application, which may include        but is not limited to contact name, organization, telephone        number, email address, www address, mailing address, physical        address, contact history, voice audio data, transcribed text        data, GPS/locational data, time and date data, calendar        information, call log data, duration of call data, video and        graphic information    -   In another embodiment, the server system may remotely process        input data and command data and interpreted data, and assemble        or individual or combined data into an output format, which may        be delivered in a variety of electronic formats. For example,        the Server System may process audio input data through a        transcription software module or service, producing output data        in the form of transcribed text, which is sent back to the        mobile device, or is forwarded directly to a user-specified        location.

In at least one embodiment, the Automated Notation Server System mayinclude a plurality of components operable to perform and/or implementvarious types of functions, operations, actions, and/or other featuressuch as, for example, one or more of the following (or combinationsthereof):

-   -   Context Interpreter (e.g., 502) which, for example, may be        operable to automatically and/or dynamically analyze contextual        criteria relating to a given event and concurrent conditions,        and automatically determine or identify the most likely actions        and/or responses to be performed. According to different        embodiments, examples of contextual criteria which may be        analyzed may include, but are not limited to, one or more of the        following (or combinations thereof):        -   location-based criteria (e.g., geolocation of client device,            geolocation of agent device, etc.)        -   time-based criteria        -   identity of Client user        -   identity of Agent user        -   user profile information        -   transaction history information        -   recent user activities        -   proximate business-related criteria (e.g., criteria which            may be used to determine whether the client device is            currently located at or near a recognized business            establishment such as a bank, gas station, restaurant,            supermarket, etc.)        -   etc.

For example, in at least one embodiment, the Automated Notation ServerSystem could determine that if a customer is using a mobile AutomatedNotation client device at the airport (Location obtained via GPS), thecustomer is planning to check in or identify himself with an airportagent.

-   -   Time Synchronization Engine (e.g., 504) which, for example, may        be operable to manages universal time synchronization (e.g., via        NTP and/or GPS)    -   Search Engine (e.g., 528) which, for example, may be operable to        search for transactions, logs, items, accounts, options in the        TIS databases    -   Configuration Engine (e.g., 532) which, for example, may be        operable to determine and configure activation and expiration        settings for one or more TIDs. In at least one embodiment, the        Configuration Engine may also be operable to manage various        types of TIS database information such as, for example, user        credit card/payment accounts, device associations, user        identification information, payment gateway information, etc.    -   Transcription Processing Component(s) (e.g., 523) which, for        example, may be operable to automatically and/or dynamically        initiate, perform, and/or facilitate transcription of audio        content into corresponding text-based content. In at least one        embodiment, the Transcription Processing Component(s) may        utilize the services of one or more remote transcription servers        for performing at least a portion of the transcription        processing. In at least one embodiment, the Automated Notation        Server System may initiate transcription of the Tote Note audio        content via use of an API to the Google Voice transcription        service (provided by Google, Inc.).    -   Time Interpreter (e.g., 518) which, for example, may be operable        to automatically and/or dynamically modify or change security        identifier activation and expiration time(s) based on various        criteria such as, for example, time, location, transaction        status, etc.    -   Authentication/Validation Component(s) (e.g., 547) (password,        software/hardware info, security identifier, SSL certificates)        which, for example, may be operable to perform various types of        authentication/validation tasks such as, for example, one or        more of the following (or combinations thereof):        -   verifying/authenticating devices,        -   verifying passwords, passcodes, SSL certificates, biometric            identification information, and/or other types of            security-related information        -   verify/validate security identifier activation and/or            expiration times        -   etc.

In one implementation, the Authentication/Validation Component(s) may beadapted to determine and/or authenticate the identity of the currentuser or owner of the mobile client system. For example, in oneembodiment, the current user may be required to perform a log in processat the mobile client system in order to access one or more features. Insome embodiments, the mobile client system may include biometricsecurity components which may be operable to validate and/orauthenticate the identity of a user by reading or scanning The usersbiometric information (e.g., fingerprints, face, voice, eye/iris, etc.).In at least one implementation, various security features may beincorporated into the mobile client system to prevent unauthorized usersfrom accessing confidential or sensitive information.

-   -   Transaction Processing Engine (e.g., 522) which, for example,        may be operable to handle various types of transaction        processing tasks such as, for example, one or more of the        following (or combinations thereof):        -   identifying/determining transaction type;        -   determining which payment gateway(s) to use;        -   associating databases information to security identifiers;        -   etc.    -   OCR Processing Engine (e.g., 534) which, for example, may be        operable to perform image processing and optical character        recognition of images such as those captured by a mobile device        camera, for example.    -   Database Manager (e.g., 526) which, for example, may be operable        to handle various types of tasks relating to database updating,        database management, database access, etc. In at least one        embodiment, the Database Manager may be operable to manage TISS        databases, Automated Notation Device Application databases,        Transaction ID Appliance databases, etc.    -   Log Component(s) (e.g., 510) which, for example, may be operable        to generate and manage transactions history logs, system errors,        connections from APIs, etc.    -   Status Tracking Component(s) (e.g., 512) which, for example, may        be operable to automatically and/or dynamically determine,        assign, and/or report updated transaction status information        based, for example, on the state of the transaction. In at least        one embodiment, the status of a given transaction may be        reported as one or more of the following (or combinations        thereof): Completed, Incomplete, Pending, Invalid, Error,        Declined, Accepted, etc.    -   Gateway Component(s) (e.g., 514) which, for example, may be        operable to facilitate and manage communications and        transactions with external Payment Gateways.    -   Web Interface Component(s) (e.g., 508) which, for example, may        be operable to facilitate and manage communications and        transactions with TIS web portal(s).    -   API Interface(s) to Automated Notation Server System(s) (e.g.,        546) which, for example, may be operable to facilitate and        manage communications and transactions with API Interface(s) to        Automated Notation Server System(s)    -   API Interface(s) to 3rd Party Server System(s) (e.g., 548)        which, for example, may be operable to facilitate and manage        communications and transactions with API Interface(s) to 3rd        Party Server System(s)    -   OCR Processing Engine (e.g., 534) which, for example, may be        operable to perform image processing and optical character        recognition of images such as those captured by a mobile device        camera, for example.    -   At least one processor 510. In at least one embodiment, the        processor(s) 510 may include one or more commonly known CPUs        which are deployed in many of today's consumer electronic        devices, such as, for example, CPUs or processors from the        Motorola or Intel family of microprocessors, etc. In an        alternative embodiment, at least one processor may be specially        designed hardware for controlling the operations of the mobile        client system. In a specific embodiment, a memory (such as        non-volatile RAM and/or ROM) also forms part of CPU. When acting        under the control of appropriate software or firmware, the CPU        may be responsible for implementing specific functions        associated with the functions of a desired network device. The        CPU preferably accomplishes one or more these functions under        the control of software including an operating system, and any        appropriate applications software.    -   Memory 516, which, for example, may include volatile memory        (e.g., RAM), non-volatile memory (e.g., disk memory, FLASH        memory, EPROMs, etc.), unalterable memory, and/or other types of        memory. In at least one implementation, the memory 516 may        include functionality similar to at least a portion of        functionality implemented by one or more commonly known memory        devices such as those described herein and/or generally known to        one having ordinary skill in the art. According to different        embodiments, one or more memories or memory modules (e.g.,        memory blocks) may be configured or designed to store data,        program instructions for the functional operations of the mobile        client system and/or other information relating to the        functionality of the various Mobile Transaction techniques        described herein. The program instructions may control the        operation of an operating system and/or one or more        applications, for example. The memory or memories may also be        configured to store data structures, metadata, Transaction ID        information/images, and/or information/data relating to other        features/functions described herein. Because such information        and program instructions may be employed to implement at least a        portion of the Automated Notation System techniques described        herein, various aspects described herein may be implemented        using machine readable media that include program instructions,        state information, etc. Examples of machine-readable media        include, but are not limited to, magnetic media such as hard        disks, floppy disks, and magnetic tape; optical media such as        CD-ROM disks; magneto-optical media such as floptical disks; and        hardware devices that are specially configured to store and        perform program instructions, such as read-only memory devices        (ROM) and random access memory (RAM). Examples of program        instructions include both machine code, such as produced by a        compiler, and files containing higher level code that may be        executed by the computer using an interpreter.    -   Interface(s) 506 which, for example, may include wired        interfaces and/or wireless interfaces. In at least one        implementation, the interface(s) 506 may include functionality        similar to at least a portion of functionality implemented by        one or more computer system interfaces such as those described        herein and/or generally known to one having ordinary skill in        the art.    -   Device driver(s) 542. In at least one implementation, the device        driver(s) 542 may include functionality similar to at least a        portion of functionality implemented by one or more computer        system driver devices such as those described herein and/or        generally known to one having ordinary skill in the art.    -   One or more display(s) 535. According to various embodiments,        such display(s) may be implemented using, for example, LCD        display technology, OLED display technology, and/or other types        of conventional display technology. In at least one        implementation, display(s) 535 may be adapted to be flexible or        bendable. Additionally, in at least one embodiment the        information displayed on display(s) 535 may utilize e-ink        technology (such as that available from E Ink Corporation,        Cambridge, Mass., www.eink.com), or other suitable technology        for reducing the power consumption of information displayed on        the display(s) 535.    -   Email Server Component(s) 536, which, for example, may be        configured or designed to provide various functions and        operations relating to email activities and communications.    -   Web Server Component(s) 537, which, for example, may be        configured or designed to provide various functions and        operations relating to web server activities and communications.    -   Messaging Server Component(s) 538, which, for example, may be        configured or designed to provide various functions and        operations relating to text messaging and/or other social        network messaging activities and/or communications.    -   Etc.

In at least one embodiment, the Tote Note Application may be configuredor designed to provide automatic assistance to users who make frequentcalls on their mobile devices and are frequently on the road or unableto make call notes during their conversations, such as sales people,executives, consultants, assistants, etc. In one embodiment, a Tote Notemay be sent directly to a user's email inbox, and may include an MP3audio attachment of the user's audio notes as well as a texttranscription of the user's audio notes within the email body. In atleast one embodiment, the email subject line may include variousinformation such as, for example, the name and phone number of theperson with whom the user spoke, timestamp information, etc. Users mayalso manually initiate recording of a new Tote Note at the user's mobilecommunication device. For corporate users, one or more Tote Note APIsare available to integrate with CRM software and/or other types of3^(rd) party systems/software.

FIGS. 10-21 illustrate example screenshots of various GUIs which may beused for facilitating activities relating to one or more of theAutomated Notation aspects disclosed herein. In at least one embodiment,at least a portion of the GUIs may be configured or designed for use atone or more mobile devices.

FIGS. 10 shows an example screenshot of an Automated Tote Note UserPrompt GUI in accordance with a specific embodiment. In at least oneembodiment, the Tote Note Application may continuously or periodicallymonitor events/conditions at the user's mobile communication device inorder to detect the occurrence of one or more triggeringevents/conditions which may cause the Tote Note Application toautomatically display Tote Note User Prompt GUI portion 1002 at theuser's device. For example, according to different embodiments, one ormore different threads or instances of the Tote Note Application may beinitiated in response to detection of one or more conditions or eventssatisfying one or more different types of minimum threshold criteria fortriggering display Tote Note User Prompt GUI portion 1002. Variousexamples of conditions or events which may trigger display of theAutomated Tote Note User Prompt GUI of FIG. 10 may include, but are notlimited to, one or more of the following (or combinations thereof):

-   -   end of phone call event;    -   email send event;    -   email receive event;    -   text message send event;    -   text message receive event;    -   time related criteria (e.g., only display of Automated Tote Note        User Prompt GUI between 9am-5pm);    -   day/date related criteria (e.g., only allow display of Automated        Tote Note User Prompt GUI between Mon-Fri; only allow display of        Automated Tote Note User Prompt GUI—see, e.g., FIG. 19);    -   contact related criteria (e.g., only allow display of Automated        Tote Note User Prompt GUI for specific contacts pre-selected by        the user), including, but not limited to, one or more of the        following (or combinations thereof):        -   Specific contact name;        -   Specific contact organization/company/business;        -   Specific industry;        -   Specific phone number (checked against a database);        -   User-specified list (i.e. “PTA members” or “Sales Team”);        -   Area code;    -   call duration criteria (e.g., only allow display of Automated        Tote Note User Prompt GUI if call duration exceeds minimum        threshold amount of time T such as, for example, T>10 seconds);    -   call frequency criteria (e.g., only allow display of Automated        Tote Note User Prompt GUI if the call frequency for a given        phone number exceeds a predetermined threshold value (TH), such        as, for example, TH≧2; Total number of incoming or outgoing        calls (e.g., greater than “x”), etc.);    -   call type criteria (e.g., only allow display of Automated Tote        Note User Prompt GUI if the call type matches one or more        specified call types such as, for example, one or more of the        following (or combinations thereof): incoming calls, outgoing        calls, failed calls, successfully ended calls, etc.);    -   voicemail receipt event (e.g., only allow display of Automated        Tote Note User Prompt GUI for a given call event if a voicemail        has been received in association with that call event);    -   and/or other types of events, conditions and/or criteria which        may be defined or specified by the user (e.g., using different        types of business rules such as regular expressions, etc.).

As illustrated in the example embodiment of FIG. 10, if the Tote NoteApplication has detected a set of conditions/events satisfying minimumthreshold criteria for triggering display Tote Note User Prompt GUIportion 1002, it may automatically display the Tote Note User Prompt GUIportion 1002 at the mobile communication device's display for apredetermined time interval (e.g., such as 6 seconds, or a differentvalue which may be defined the user), thereby prompting the user toinitiate recording of a Tote Note, if desired by the user. In at leastone embodiment, if the user desires not to initiate recording of a ToteNote, the user may provide input (e.g., tapping “NO”, tapping on “X”,verbally stating “NO”, etc.) to close the displayed Tote Note UserPrompt GUI portion 1002. In at least one embodiment, the user may desireto create a related calendar event (e.g., by tapping on ‘Add CalendarEvent” button 1006) rather than (or in addition to) recording a ToteNote.

In at least one embodiment, if the user desires to initiate recording ofa Tote Note, the user may provide input (e.g., tapping “YES”, verballystating “YES”, etc.) to cause the Tote Note Application to initiaterecording of a new Tote Note to be associated with the recently detectedset of conditions/events.

FIG. 11 shows an example screenshot of a Tote Note Recording GUI inaccordance with a specific embodiment. In at least one embodiment, aspart of the process of initiating recording of a new Tote Note, the ToteNote Application may display Tote Note Recording GUI portion 1102 at theuser's mobile communication device to facilitate the user and recordingof the new Tote Note. For example, as illustrated in the exampleembodiment of FIG. 11, Tote Note Recording GUI portion 1102 may includeone or more of the following features, objects, and/or content (orcombinations thereof):

-   -   Tote Note record/pause button 1112 which, for example, may be        toggled by the user to pause and/or commence recording of the        new Tote Note;    -   Re-record button 1104 for initiating re-recording of the new        Tote Note;    -   Send button 1106, which, for example, may be tapped by the user        to indicate to the Tote Note Application that the user has        completed recording of the new Tote Note, and now desires to        finalize and send the new Tote Note;    -   Elapsed recording time content 1110, which, for example, may        track the total time length of the new Tote Note which is being        recorded;    -   Maximum recording time content 1111, which, for example, may        display the maximum total amount of recording time available for        recording of the new Tote Note;    -   Add Tag button 1108, which, for example, may be configured or        designed to enable the user to tag the new Tote Note with one or        more tags selected by the user. In at least one embodiment, if        the user taps the ADD TAGS button, 1108, the Tote Note        Application may respond by displaying a Tote Note Tagging GUI        (not shown) which is configured or designed to enable the user        to associate the new Tote Note with one or more predefined tags        (e.g., dynamically suggested) and/or one or more tags which may        be manually input by the user.

In at least one embodiment, the audio portion of the new Tote Note maybe record locally at the mobile communication device (e.g., using thedevice's microphone), and may be stored temporarily in local memory ofthe mobile communication device. According to different embodiments, theaudio portion of the new Tote Note may be recorded and saved in avariety of different audio formats such as, for example, MP3, WAV, ACC,FLAC, OGG, FLASH, etc. In some embodiments, the Tote Note Applicationmay continue recording and caching the audio portion of the new ToteNote in local memory of the mobile communication device, and mayasynchronously upload the new Tote Note audio file to the AutomatedNotation Server System after the user taps the Send button 1106.Alternatively, in other embodiments, the Tote Note Application maycommence streaming of the audio portion of the new Tote Note to theAutomated Notation Server System (and/or other remote transcriptionservice) in real-time, as the mobile communication device captures theaudio content from the user.

FIG. 12 shows an example screenshot of a Tote Note Processing GUI inaccordance with a specific embodiment. In at least one embodiment, theTote Note Application may be displayed in response to the user tappingthe SEND button 1106 (FIG. 11).

FIGS. 13-15 show example screenshots of various Tote Note UserOptions/Preferences GUIs in accordance with a specific embodiment. In atleast one embodiment, the Tote Note User Options/Preferences GUIs may beconfigured or designed to enable the user to configure various types ofoptions and/or preferences associated with the Tote Note Applicationsuch as, for example, one or more of the following (or combinationsthereof):

-   -   Always Active (1302): check this box if the user wants the Tote        Note Application to enable running of the Tote Note Application        (e.g., including running in background) at all (or desired)        times.    -   Active Hours (1304)—User may configure this setting to set the        times when The Tote Note Application is be active on a user's        mobile device. During active hours, the user will receive a        prompt at the end of one or more call asking “Would the user        like to record a Tote Note?” The user may tap YES, or NO, or the        box may disappear by itself after a few seconds. (See the “Timer        Settings” section for more information about the pop-up box.).        For example, the user may configure the Tote Note Application to        be active only at certain times, as determined (and customized)        by the user. If the user wants The Tote Note Application to be        active only during business hours (8AM to 6PM Monday through        Friday), the user may check the box at 1304.    -   Dialog Box Time Limit (1310) refers to the length of time that        the Tote Note User Prompt GUI dialog box is to be displayed on        the mobile communication device (e.g., after a call end event is        detected). In at least one embodiment, the user may operate the        slider at 1310 to set this timer between 2 and 10 seconds. Some        users prefer to set this at around 5-6 seconds.    -   Max Recording Time is the maximum length of time for a single        Tote Note. In at least one embodiment, this value may be        customizable by the user. In other embodiments, this value may        be set or determined by other conditions such as, for example,        the type of Tote Note subscription service associated with the        users account. For example, a FREE version of the Tote Note        subscription service may allow the user to set the timer up to a        maximum of 30 seconds (note: in at least one embodiment, the        user may also have an extra second or two after 30 seconds if        needed). In at least one embodiment, a PRO version of the Tote        Note subscription service may allow the user to set the timer up        to a maximum of 2 full minutes per Tote Note.    -   Outgoing Email Settings (not shown)—In at least one embodiment,        the Tote Note Application may be configured or designed to use a        user's web-based email address to send one or more Tote Notes.        Examples of some of the more common e-mail services include, for        example, Gmail, Yahoo Mail, Hotmail, Windows Live, etc.    -   Outgoing Email Address—In at least one embodiment, the user may        enter the “FROM” email address to be used for identifying the        source or origin of Tote Note e-mail messages created by and/or        sent by the user.    -   Destination Email Address (1404, FIG. 14)—in at least one        embodiment the user may provide a “TO” email address to be used        for delivering Tote Note e-mail messages such as those created        by and/or sent by the user.    -   Secondary Email Address (1410)—In at least one embodiment, a        user's Tote Note to be sent to another email address, in        addition to the primary destination address. For example, the        user may elect to “cc” an assistant on Tote Note activities to        allow the assistant to be timely updated about important call        details, etc. In at least one embodiment, the secondary e-mail        address functionality may be only available in the PRO Version        of Tote Notes.

FIGS. 16-19 show example screenshots of various Tote Note AutomatedSet-Up GUIs in accordance with a specific embodiment. In at least oneembodiment, the Tote Note Application may

The Tote Note Application may be configured or designed to allow theuser to complete the initial setup of the application in less than 30seconds. At initial startup, a user may be led through an automated ToteNote Setup Wizard, where the user is automatically prompted for desiredinput information. Example screenshots of the automated Tote Note SetupWizard are illustrated in FIGS. 16-19.

FIG. 20 shows an example screenshot of a Tote Note History GUI inaccordance with a specific embodiment. As illustrated in the exampleembodiment of FIG. 20, the Tote Note History GUI may include a varietyof different content and/or features such as, for example, one or moreof the following (or combinations thereof):

-   -   Tote Note History Tab 2001;    -   Tote Note Help Tab 2003;    -   Tote Note History information 2010, which, for example, may        include a log of individual records (e.g., 2012, 2014, 2016)        relating to previously created Tote Notes.    -   Tote Note Preferences button 2022 for providing a user with        access to the Tote Note Application preferences and/or options;    -   Clear Tote Notes history button 2024;    -   etc.

FIG. 21 shows an example screenshot of a Tote Note Contact GUI inaccordance with a specific embodiment. As illustrated in the exampleembodiment of FIG. 21, the Tote Note Contact GUI may include a varietyof different content and/or features such as, for example, one or moreof the following (or combinations thereof):

-   -   Contact Name information 2101;    -   Other types of contact-related information 2110 (e.g., phone        numbers, email addresses, postal addresses, work-related        information, etc.);    -   Tote Note Contact Enable/Disable GUI 2120 which, for example,        may be configured or designed to allow a user to selectively        enable/disable Tote Note functionality on a per contact basis.        For example, as illustrated in the example embodiment of FIG.        21, the user may selectively enable (or disable) implementation        of automated Tote Note functionality in connection with events        relating to contact information associated with David Flynn        (2101). In some embodiments, the Tote Note Application may also        be configured or designed to enable a user to selectively        enable/disable Tote Note functionality for selected groups of        contacts such as, for example, friends, relatives, business        associates, etc.

FIG. 22 shows an example screenshot of a different embodiment of a ToteNote User Prompt GUI 2200. For example, in at least one embodiment, atthe conclusion of a call, the Tote Note Application may automaticallydisplay Tote Note User Prompt GUI 2200, which may prompt the user toperform one or more additional activities, if desired. For example, asillustrated in the example embodiment of FIG. 22, the Tote Note UserPrompt GUI 2200 may prompt the user to initiate or perform one or moreof the following actions/activities (or combinations thereof):

-   -   Send a copy of the user's latest Tote Note to someone else        (2212). In one embodiment, the user may select this option to        send a copy of the most recent Tote Note to another party,        database, email address, text message destination, or other        method of electronic messaging. In one embodiment, the user may        be able to augment the original Tote Note prior to sending.    -   Send a Call Log Summary to the most recent person in the mobile        communication device's call history (e.g., Janet Varona)        (2214).). In one embodiment, the user may select this option to        send a call log summary that may be comprised of metadata to        another party, database, email address, text message        destination, or other method of electronic messaging to the        person with whom the user just spoke. For example, to convey        time spent on the call for billing or invoicing purposes.    -   Record and Send a new Tote Note to someone (2216). In one        embodiment, the user may select this option to record and send a        new Tote Note to an intended recipient.    -   Add additional content to an existing Tote Note (2218). In one        embodiment, the user may select this option to augment or append        to a previously sent Tote Note. In one embodiment, a user could        select a Tote Notes that was previously sent and stored in the        Cloud, which could be appended, or re-sent, or sent to another        contact, or delete as needed.    -   Perform another Tote Note activity (2220). ). In one embodiment,        the user may select this option to initiate or perform other        possible actions which the Tote Note Application may anticipate        that the user might want to do in response to different detected        events/conditions such as, for example: end of call, dropped        call, missed call, end of voicemail playback, etc. For example,        in one embodiment, if the Tote Note Application detects a        dropped call event, it might ask the user if he wants to (a)        record and send a Tote Note to the dropped caller; (2) send        dropped caller a pre-written message such as “Will call you back        shortly when there's better cell phone reception”; (3) set a        reminder to call the dropped caller back; etc. Other Tote Note        activities may include, but are not limited to, one or more of        the following (or combinations thereof): add a calendar item,        update a social media status, use voice commands to open other        software applications (such as a mapping function when the user        speaks “where is Café Claude”, or interfaces with another type        of digital assistant software to answer user inquiries “what is        the probability of rain today”).

FIG. 6 shows an example screenshot of an email interface 600 inaccordance with a specific embodiment. As illustrated in the exampleembodiment of FIG. 6, the email interface 600 includes an inbox displayportion 620 which displays content relating to a plurality of differentTote Note email message records (e.g., 622, 624, 626, etc.). In at leastone embodiment, each Tote Note email message record may includeinformation relating to a respective Tote Note creation event which, forexample, was recorded at the user's mobile communication device. Forexample, as illustrated in the example embodiment of FIG. 6, Tote Noteemail message record 622 includes a subject line 623 which includescontent relating to various information such as, for example, the nameand phone number of the person with whom the user spoke, timestampinformation, etc. Tote Note email message record 622 also includes anaudio attachment (e.g., 614) of the user's audio notes relating to thecall (as identified in the subject line), as well as a texttranscription (e.g., 612) of the users audio notes within the emailbody.

Example Procedures and Flow Diagrams

FIGS. 7-8 illustrate various example embodiments of different AutomatedNotation System procedures and/or procedural flows which may be used forfacilitating activities relating to one or more of the AutomatedNotation System aspects disclosed herein.

According to different embodiments, at least a portion of the varioustypes of functions, operations, actions, and/or other features providedby the Automated Notation System Procedures of FIGS. 7-8 may beimplemented at one or more client systems(s), at one or more serversystems (s), and/or combinations thereof.

In at least one embodiment, one or more of the Automated Notation Systemprocedures may be operable to utilize and/or generate various differenttypes of data and/or other types of information when performing specifictasks and/or operations. This may include, for example, inputdata/information and/or output data/information. For example, in atleast one embodiment, the Automated Notation System procedures may beoperable to access, process, and/or otherwise utilize information fromone or more different types of sources, such as, for example, one ormore local and/or remote memories, devices and/or systems. Additionally,in at least one embodiment, the Automated Notation System procedures maybe operable to generate one or more different types of outputdata/information, which, for example, may be stored in memory of one ormore local and/or remote devices and/or systems. Examples of differenttypes of input data/information and/or output data/information which maybe accessed and/or utilized by the Automated Notation System proceduresmay include, but are not limited to, one or more of those describedand/or referenced herein.

In at least one embodiment, a given instance of the Automated NotationSystem procedures may access and/or utilize information from one or moreassociated databases. In at least one embodiment, at least a portion ofthe database information may be accessed via communication with one ormore local and/or remote memory devices. Examples of different types ofdata which may be accessed by the Automated Notation System proceduresmay include, but are not limited to, one or more of those describedand/or referenced herein.

According to specific embodiments, multiple instances or threads of theAutomated Notation System procedures may be concurrently implementedand/or initiated via the use of one or more processors and/or othercombinations of hardware and/or hardware and software. For example, inat least some embodiments, various aspects, features, and/orfunctionalities of the Automated Notation System procedures may beperformed, implemented and/or initiated by one or more of the varioussystems, components, systems, devices, procedures, processes, etc.,described and/or referenced herein.

According to different embodiments, one or more different threads orinstances of the Automated Notation System procedures may be initiatedin response to detection of one or more conditions or events satisfyingone or more different types of minimum threshold criteria for triggeringinitiation of at least one instance of the Automated Notation Systemprocedures. Various examples of conditions or events which may triggerinitiation and/or implementation of one or more different threads orinstances of the Automated Notation System procedures may include, butare not limited to, one or more of those described and/or referencedherein.

According to different embodiments, one or more different threads orinstances of the Automated Notation System procedures may be initiatedand/or implemented manually, automatically, statically, dynamically,concurrently, and/or combinations thereof. Additionally, differentinstances and/or embodiments of the Automated Notation System proceduresmay be initiated at one or more different time intervals (e.g., during aspecific time interval, at regular periodic intervals, at irregularperiodic intervals, upon demand, etc.).

In at least one embodiment, initial configuration of a given instance ofthe Automated Notation System procedures may be performed using one ormore different types of initialization parameters. In at least oneembodiment, at least a portion of the initialization parameters may beaccessed via communication with one or more local and/or remote memorydevices. In at least one embodiment, at least a portion of theinitialization parameters provided to an instance of the AutomatedNotation System procedures may correspond to and/or may be derived fromthe input data/information.

FIG. 7 shows an example of a Tote Note Creation Procedure 700 inaccordance with a specific embodiment. In at least one embodiment, atleast a portion of the actions and/or operations implemented and/orinitiated by the Tote Note Creation Procedure may be performed by theTote Note Application running on the user's mobile communication device.

As illustrated in the example embodiment of FIG. 7, at 702initialization & initial set-up of the Tote Note Application may beperformed.

In at least one embodiment, at 704, a determination may be made as towhether or not a set of condition(s) and/or event(s) has been detectedwhich meet or exceed a minimum set of threshold criteria. For example,as illustrated in the example embodiment of FIG. 7 at 704, adetermination may be made as to whether or not an End of Call (EoC)event has been detected which satisfies minimum threshold criteria.According to different embodiments, examples of such minimum thresholdcriteria may include, but are not limited to, one or more of thefollowing (or combinations thereof): which may be defined for triggeringwhich may trigger display of the Automated Tote Note User Prompt GUI ofFIG. 10 may include, but are not limited to, one or more of thefollowing (or combinations thereof):

-   -   time related criteria;    -   day/date related criteria;    -   contact related criteria such as, for example, one or more of        the following (or combinations thereof):        -   Specific contact name;        -   Specific contact organization/company/business;        -   Specific industry;        -   Specific phone number (checked against a database);        -   User-specified list (i.e. “PTA members” or “Sales Team”);        -   Area code;    -   call duration criteria;    -   call frequency criteria;    -   call type criteria;    -   and/or other types of events, conditions and/or criteria which        may be defined or specified by the user (e.g., using different        types of business rules such as regular expressions, etc.).

As illustrated in the example embodiment of FIG. 7, if it is determinedthat a set of condition(s)/event(s) meets (or exceeds) the specifiedthreshold criteria, one or more response(s) may be initiated, which, forexample, may include, but is not limited to, acquiring, detecting and/oranalyzing conditions, criteria and/or other information relating toidentified EoC event (706).

As illustrated in the example embodiment of FIG. 7, at 708 adetermination may be made as to whether or not to automatically displaythe Tote Note User Prompt GUI based on detectedconditions/criteria/information. For example, in at least oneembodiment, additional conditions, criteria, and/or other informationmay be analyzed to determine whether or not such conditions, criteria,and/or information meets or exceeds additional threshold criteria. Forexample, in one embodiment, after an EoC event has been detected (e.g.,at 704), the Tote Note Application may access the mobile communicationdevice's call log in order to acquire (e.g., 706) EoC-relatedinformation such as, for example, one or more of the following (orcombinations thereof): the duration of the phone call associated withthe EoC event, the phone number associated with the EoC event, thedate/time when the phone call was initiated, and the date/time when thephone call ended. The Tote Note Application may then analyze theacquired EoC-related information in order to determine (e.g., 708)whether or not the analyzed information meets or exceeds predefinedcriteria for initiating automatic display of the Tote Note User PromptGUI.

In at least one embodiment, if it is determined (e.g., at 708) that theTote Note User Prompt GUI may be automatically displayed at the user'smobile communication device, the Tote Note Creation Procedure mayrespond by causing the Tote Note User Prompt GUI to be automaticallydisplayed at the mobile communication device. In at least oneembodiment, the Tote Note User Prompt GUI may be cause to beautomatically displayed at the mobile communication device for apredefined time interval (e.g., 6 seconds).

As shown at 712, the Tote Note Creation Procedure may wait to receiveinput or confirmation from the user to initiate creation of a new ToteNote, and to begin recording of the Tote Note's audio content. In atleast one embodiment, a user may tap on the “YES” button (1011, FIG. 10)of the Tote Note User Prompt GUI to initiate creation of a new ToteNote, and begin recording of the Tote Note's audio content and/orrecording of other types of media/content. In at least one embodiment,at least a portion of the recorded Tote Note media content may bestored, at least temporarily, in local memory of the mobilecommunication device.

In at least one embodiment, as part of the process of creating the newTote Note, the Tote Note Creation Procedure may also perform one or moreadditional operations for acquiring additional content, data, metadata,and/or other information relating to identified EoC event (and/orrelating to the newly created Tote Note). In at least one embodiment,examples of such additional content, data, metadata, and/or otherinformation may include, but are not limited to, one or more of thefollowing (or combinations thereof):

-   -   contact information (e.g., contact name(s), phone number(s),        e-mail address(es), lable(s), etc.);    -   picture/image content;    -   video content;    -   text content;    -   call history (or call log) information;    -   call duration information;    -   user account information;    -   user profile information;    -   metadata;    -   tags (e.g., to be associated with new Tote Note);    -   communication history information (e.g., relating to prior        communications between user and other parties);    -   time/date information;    -   etc.

As shown at 712, the Tote Note Creation Procedure may wait to detect oneor more condition(s)/event(s) for ending recording of the Tote Notemedia content. For example, in at least one embodiment, the user may tapon the “SEND” button (1106, FIG. 11) of the Tote Note Recording GUI toindicate to the Tote Note Application that the user has completedrecording of the new Tote Note, and desires to finalize and send/uploadthe new Tote Note.

As illustrated in the example embodiment of FIG. 7, upon detection ofone or more condition(s)/event(s) for ending recording of the Tote Notemedia, one or more response(s) may be automatically initiated which, forexample, may include, but are not limited to, one or more of thefollowing (or combinations thereof):

-   -   End recording of Tote Note media content;    -   Initiate Tote Note Processing and Distribution Procedure (e.g.,        FIG. 8);    -   Provide (e.g., transmit or upload) recorded Tote Note media        content and acquired related content/metadata/information to        Automated Notation Server System;    -   etc.

It will be appreciated that different embodiments of the Tote NoteCreation Procedure (not shown) may include additional features and/oroperations than those illustrated in the specific embodiment of FIG. 7,and/or may omit at least a portion of the features and/or operations ofthe Tote Note Creation Procedure illustrated in the specific embodimentof FIG. 7.

FIG. 8 shows an example of a Tote Note Processing & DistributionProcedure 800 in accordance with a specific embodiment. In at least oneembodiment, at least a portion of the actions and/or operationsimplemented and/or initiated by the Tote Note Processing & DistributionProcedure may be performed by the Automated Notation Server System.

As illustrated in the example embodiment of FIG. 8, at 802, Tote NoteCreation Data may be received. In at least one embodiment, the ReceiveTote Note Creation Data may include, for example, recorded Tote Notemedia content and/or additional content, data, metadata, and/or otherinformation relating to an identified EoC event and/or relating to a newTote Note to be created.

As illustrated in the example embodiment of FIG. 8, at 804, the ToteNote Processing & Distribution Procedure may analyze and parse thereceived Tote Note media content into chunks (“Parsed Media Chunks”).For example, in one embodiment, the recorded Tote Note media content(received at the Automated Notation Server System), includes recordedaudio content which may be analyzed and parsed into chunks. In at leastone embodiment, each chunk of parsed content may have an associated timeduration which does not exceed a maximum duration value (e.g., max=20sec) and/or which is within a range of preferred duration values (e.g.,preferred chunk duration value range=18 sec-20 sec).

In at least one embodiment, the parsing of the recorded audio contentmay include analyzing the audio content for gaps of silence (or lowaudio output), and using at least a portion of the identified “lowaudio” gaps to parse the audio content into discrete chunks of audiocontent (e.g., of about 18-20 sec each).

As illustrated in the example embodiment of FIG. 8, at 806, the ParsedMedia Chunks may be sent to (or forwarded to) a Transcription Servicefor transcribing the audio chunk files into text. In at least oneembodiment, a remote transcription service such as that available viathe Google Voice API may be used. In other embodiments, the AutomatedNotation Server System includes functionality for performing at least aportion of the transcription operations.

In the specific example embodiment of FIG. 8, it is assumed at 806 thatthe Tote Note Processing & Distribution Procedure receives text datafrom the Transcription Service relating to transcription of Parsed MediaChunks.

As illustrated in the example embodiment of FIG. 8, at 808, a Tote Notemessage may be generated using the received Tote Note transcription dataand received Tote Note Creation Data, and/or other related information,content, and/or metadata. In at least one embodiment, a texttranscription of the audio Tote Note content (and related metadata) maybe included as text info in the Tote Note message body. In at least oneembodiment, the audio Tote Note content (as well as other types of ToteNote content) may be attached as files to the Tote Note message.

As illustrated in the example embodiment of FIG. 8, at 810, the newlygenerated Tote Note message may be transmitted (e.g., via email, text,etc.) to user's mobile communication device and/or to other desireddevice(s)/system(s) such as, for example, the user's specified emailserver.

In at least one embodiment, one or more copies of the Tote Note message(and its associated media content) may be stored at the AutomatedNotation Server System and/or other online storage system(s). In atleast one embodiment, the Automated Notation Server System may beconfigured or designed to include functionality to stream text & audioand other media/content to a user's mobile communication device, whichmay be accessed and presented to a user via the Tote Note Application.

It will be appreciated that different embodiments of the Tote NoteProcessing & Distribution Procedure (not shown) may include additionalfeatures and/or operations than those illustrated in the specificembodiment of FIG. 8, and/or may omit at least a portion of the featuresand/or operations of the Tote Note Processing & Distribution Procedureillustrated in the specific embodiment of FIG. 8.

It may be appreciated that different embodiments of the AutomatedNotation Procedure(s) (not shown) may include additional features and/oroperations than those illustrated in the specific embodiments explicitlydescribed herein, and/or may omit at least a portion of the featuresand/or operations of Automated Notation Procedure(s) explicitlydescribed herein.

Although several example embodiments of one or more aspects and/orfeatures have been described in detail herein with reference to theaccompanying drawings, it is to be understood that aspects and/orfeatures are not limited to these precise embodiments, and that variouschanges and modifications may be effected therein by one skilled in theart without departing from the scope of spirit of the invention(s) asdefined, for example, in the appended claims.

I claim:
 1. A computer implemented method for automated notation systemon a mobile device, the computer implemented method comprising causingat least one processor in the mobile device to execute a plurality ofinstructions for: identifying a set of threshold criteria for causing adisplay, on the mobile device, of a first user interface prompting auser associated with the mobile device to initiate a procedure at themobile device, the threshold criteria pertaining to a call eventinvolving one of incoming calls, outgoing calls, failed calls, andsuccessfully ended calls; determining when an end of the call event hasbeen detected at the mobile device; displaying a second interface at themobile communication device, when the set of threshold criteria has beensatisfied, to allow the user to enter a message related to the callevent, wherein the message is in a form of voice, email or text; andtransmitting the message to a designated destination specified by theuser.
 2. The computer implemented method as recited in claim 1, whereinthe second interface facilitates the user to access a database.
 3. Thecomputer implemented method as recited in claim 2, wherein the databaseis a contact list residing in the mobile device.
 4. The computerimplemented method as recited in claim 2, wherein the designateddestination is a place where the message is retrieved by the user whenneeded.
 5. The computer implemented method as recited in claim 2,wherein the designated destination is a place where the message isretrieved by another user when needed.
 6. The computer implementedmethod as recited in claim 2, wherein the designated destination is anemail address.
 7. The computer implemented method as recited in claim 6,wherein the email message includes a subject heading automaticallypopulated with information related to the phone call.
 8. The computerimplemented method as recited in claim 8, wherein the information is aname of a person with whom the call event occurred, date and/or time ofthe call event.
 9. The computer implemented method as recited in claim1, further comprising transcribing the message into text when themessage is in the form of voice.
 10. The computer implemented method asrecited in claim 1, further comprising initiating an instance to a CRMproduct.
 11. An apparatus comprising: at least one processor; at leastone interface operable to provide a communication link to at least onenetwork device; a display screen; memory; the at least one processorbeing operable to execute the plurality of instructions stored in thememory, and being operable to operate with the memory and the at leastone interface for: identifying a set of threshold criteria for causing adisplay, on the mobile device, of a first user interface prompting auser associated with the mobile device to initiate a procedure at themobile device, the threshold criteria pertaining to a call eventinvolving one of incoming calls, outgoing calls, failed calls, andsuccessfully ended calls; determining when an end of the call event hasbeen detected at the mobile device; displaying a second interface at themobile communication device, when the set of threshold criteria has beensatisfied, to allow the user to enter a message related to the callevent, wherein the message is in a form of voice, email or text; andtransmitting the message to a designated destination specified by theuser.
 12. The apparatus as recited in claim 11, wherein the secondinterface facilitates the user to access a database.
 13. The apparatusas recited in claim 12, wherein the database is a contact list residingin the mobile device.
 14. The apparatus as recited in claim 12, whereinthe designated destination is a place where the message is retrieved bythe user when needed.
 15. The apparatus as recited in claim 12, whereinthe designated destination is a place where the message is retrieved byanother user when needed.
 16. The apparatus as recited in claim 12,wherein the designated destination is an email address.
 17. Theapparatus as recited in claim 16, wherein the email message includes asubject heading automatically populated with information related to thephone call.
 18. The apparatus as recited in claim 18, wherein theinformation is a name of a person with whom the call event occurred,date and/or time of the call event.
 19. The apparatus as recited inclaim 11, further comprising transcribing the message into text when themessage is in the form of voice.
 20. The apparatus as recited in claim11, further comprising initiating an instance to a CRM product.